Add pico_set_modified_binary_type function #2137
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allows creating binaries using an existing binary type & linker script, but with modified RAM/SCRATCH addresses For example, to only use SRAM1 so you can power down SRAM0 in your binary you could use `pico_set_modified_binary_type(<my_exe> no_flash RAM "0x20040000" "256k"`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a function to create binaries using an existing binary type & linker script, but with modified RAM/SCRATCH addresses
A similar function is already in use by the encrypted bootloader example, and picotool xip_ram_perms binary, so this extends those by adding scratch address modification
For example, to only use SRAM1 so you can power down SRAM0 in your binary you could use
To create a XIP_SRAM only binary you could use
pico_set_modified_binary_type(<my_exe> no_flash RAM "0x13ffc000" "12k" SCRATCH_X "0x13fff000" "2k" SCRATCH_Y "0x13fff800" "2k")The existing
memmap_blocked_ram.ldcould be created using